-
Notifications
You must be signed in to change notification settings - Fork 29.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: modernize JS and tighten equality checking in test-child-process-detached #8580
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please revisit commit message to match contribution guidelines. Also what refers flankyness to? Otherwise LGTM |
Revisited the commit mesage. |
Maybe we could get @addaleax or @thealphanerd or @jasnell to give a LGTM and I merge it. |
@wzoom Also just a tip for future contributions, as you will get more familiar with |
Thanks. I did just that (ammend), but somehow git forced me to merge afterwards :/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I don't see how this addresses any flakiness though. Also, would you care to take a crack at squashing the commits.
993830f
to
1c95f1d
Compare
Removed the useless commits, now it should be ok. Flankyness was a mistake. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one nit addressed
var spawn = require('child_process').spawn; | ||
var childPath = path.join(common.fixturesDir, | ||
const spawn = require('child_process').spawn; | ||
const childPath = path.join(common.fixturesDir, | ||
'parent-process-nonpersistent.js'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can you indent this line 2 characters so that the arguments to path.join
are still aligned?
Changed var --> const and let. Changed assert.equal !== --> assert.notStrictEqual Correctly aligned argument
1c95f1d
to
617be60
Compare
FYI @addaleax Fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, landing…
Okay, I’m not going to land this without a proper CI run, so, CI: https://ci.nodejs.org/job/node-test-commit/5175/ |
Landed in d59074c! Thanks for your contribution! 🎉 |
Changed var --> const and let. Changed assert.equal !== --> assert.notStrictEqual Correctly aligned argument PR-URL: #8580 Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Changed var --> const and let. Changed assert.equal !== --> assert.notStrictEqual Correctly aligned argument PR-URL: #8580 Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
test
Description of change
Cleanup according to nodejs/code-and-learn#56